Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7941a13a162ce558c5394c9ee2e201d2d70f6b151733d78cbc506695306a5fb

Tx prefix hash: 41697adb33a26b1c9021f45fdb63755eaa047690686e11cb27543bd17dbd4dcd
Tx public key: 309a453f42980c6b80f81cf5b7e5c3a89b5159eee9d4446f50f2836b82b3c88e
Timestamp: 1741038281 Timestamp [UCT]: 2025-03-03 21:44:41 Age [y:d:h:m:s]: 00:263:02:18:21
Block: 1231513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185781 RingCT/type: yes/0
Extra: 01309a453f42980c6b80f81cf5b7e5c3a89b5159eee9d4446f50f2836b82b3c88e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 285073f68da7fb648c96a4400eb993a6025357e932855b12072e2258184b5bd3 0.600000000000 1718420 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": 1231523, "vin": [ { "gen": { "height": 1231513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "285073f68da7fb648c96a4400eb993a6025357e932855b12072e2258184b5bd3" } } ], "extra": [ 1, 48, 154, 69, 63, 66, 152, 12, 107, 128, 248, 28, 245, 183, 229, 195, 168, 155, 81, 89, 238, 233, 212, 68, 111, 80, 242, 131, 107, 130, 179, 200, 142, 2, 17, 0, 0, 0, 1, 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