Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92fbfddb2aa5d50275370d3c31ce3e0d2f52a91d39a3a71d825699f62d6d50e4

Tx prefix hash: d04539fb8d1da786a2b489dfcafabb49cfd374ff0313784279d6993ad160e0a7
Tx public key: 2b3af1d97b801df0036b3496eeea244594eb643b7ddf596b0ce8213964753be6
Timestamp: 1736578408 Timestamp [UCT]: 2025-01-11 06:53:28 Age [y:d:h:m:s]: 00:067:10:42:35
Block: 1194863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47990 RingCT/type: yes/0
Extra: 012b3af1d97b801df0036b3496eeea244594eb643b7ddf596b0ce8213964753be602110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ab7f52c02e27e349fa025c4fb316dd579bdd4fec4a00b6aff4d0ecba7d5a67a 0.600000000000 1681442 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": 1194873, "vin": [ { "gen": { "height": 1194863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ab7f52c02e27e349fa025c4fb316dd579bdd4fec4a00b6aff4d0ecba7d5a67a" } } ], "extra": [ 1, 43, 58, 241, 217, 123, 128, 29, 240, 3, 107, 52, 150, 238, 234, 36, 69, 148, 235, 100, 59, 125, 223, 89, 107, 12, 232, 33, 57, 100, 117, 59, 230, 2, 17, 0, 0, 0, 13, 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