Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b343472aaa122417d21fe52b23d5412053acc39c8fcf29e172748f4b28cce350

Tx prefix hash: 8f8df036b756977b65c5ee30784187c7e9ee4511aef5bc9ab88b6351445e6b89
Tx public key: a64aa343abd0cde1f8bcb96d6863f64ae3aa71eee96ccd4e811818a0e71157d8
Timestamp: 1731618265 Timestamp [UCT]: 2024-11-14 21:04:25 Age [y:d:h:m:s]: 00:188:01:36:21
Block: 1153789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134267 RingCT/type: yes/0
Extra: 01a64aa343abd0cde1f8bcb96d6863f64ae3aa71eee96ccd4e811818a0e71157d8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00ffcdef90aaa1458aa22b566985a8cb565ec28e4cf410a840580f4bd2fc0ccb 0.600000000000 1639400 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": 1153799, "vin": [ { "gen": { "height": 1153789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00ffcdef90aaa1458aa22b566985a8cb565ec28e4cf410a840580f4bd2fc0ccb" } } ], "extra": [ 1, 166, 74, 163, 67, 171, 208, 205, 225, 248, 188, 185, 109, 104, 99, 246, 74, 227, 170, 113, 238, 233, 108, 205, 78, 129, 24, 24, 160, 231, 17, 87, 216, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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