Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 912129d2e0e07188b937e0a37d4aa608f6ab27f236b10541edc3f434bf6c394f

Tx prefix hash: bb93680d369fa273e05b0dc1920e1a7ca5cc78c400b5f19389170dd27be5fdf2
Tx public key: a4ae92e9be5782e78b6b1799d37ead4b4d2c76fdbff8ac6a72fd9d7f97b4eb66
Timestamp: 1733812911 Timestamp [UCT]: 2024-12-10 06:41:51 Age [y:d:h:m:s]: 00:346:11:44:49
Block: 1171973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245155 RingCT/type: yes/0
Extra: 01a4ae92e9be5782e78b6b1799d37ead4b4d2c76fdbff8ac6a72fd9d7f97b4eb66021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ce56682820e1cdce913864cb169e8c0cdec259b568c8b24b2cafdbd25e0ec6 0.600000000000 1657804 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": 1171983, "vin": [ { "gen": { "height": 1171973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ce56682820e1cdce913864cb169e8c0cdec259b568c8b24b2cafdbd25e0ec6" } } ], "extra": [ 1, 164, 174, 146, 233, 190, 87, 130, 231, 139, 107, 23, 153, 211, 126, 173, 75, 77, 44, 118, 253, 191, 248, 172, 106, 114, 253, 157, 127, 151, 180, 235, 102, 2, 17, 0, 0, 0, 2, 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