Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f99d37d15eecefb84f76c1b384e644c9dee798605afc2a7d9353fa7eb7cc67ed

Tx prefix hash: 6b68081362cecd495a8e8180b6a5cc453ebba4eec30075a55a97c7fa450bea54
Tx public key: a78bc49c5d26c2149d544d0a4c0c8b6f75c96efec9bf81cb6e86bd308fae7230
Timestamp: 1714589076 Timestamp [UCT]: 2024-05-01 18:44:36 Age [y:d:h:m:s]: 01:189:08:56:13
Block: 1012696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393969 RingCT/type: yes/0
Extra: 01a78bc49c5d26c2149d544d0a4c0c8b6f75c96efec9bf81cb6e86bd308fae723002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46fe691bb02304097c2faec252ddf588a56453a7a450ede0bcb9e5085eeb9050 0.600000000000 1475300 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1012706, "vin": [ { "gen": { "height": 1012696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46fe691bb02304097c2faec252ddf588a56453a7a450ede0bcb9e5085eeb9050" } } ], "extra": [ 1, 167, 139, 196, 156, 93, 38, 194, 20, 157, 84, 77, 10, 76, 12, 139, 111, 117, 201, 110, 254, 201, 191, 129, 203, 110, 134, 189, 48, 143, 174, 114, 48, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8