Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997c89744f69bad2cd448f5e0032d4adc7b245d6acec5bfecfe61db3693bfaf6

Tx prefix hash: e57be14a514dac6892f1c9536aca5e9854203d1f1435aa6e1a823a4984e3b727
Tx public key: 1fd55a4fd3a27d3a61ff1628cb5a4a0dd87514d6dc74aa9d1c655e069fa26244
Timestamp: 1733043888 Timestamp [UCT]: 2024-12-01 09:04:48 Age [y:d:h:m:s]: 00:113:13:59:51
Block: 1165607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80958 RingCT/type: yes/0
Extra: 011fd55a4fd3a27d3a61ff1628cb5a4a0dd87514d6dc74aa9d1c655e069fa26244021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db4d3ec3593a0aa293776dbcde9b409eaaa6406fb50d42cfbf70ee8cb40d00be 0.600000000000 1651282 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": 1165617, "vin": [ { "gen": { "height": 1165607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db4d3ec3593a0aa293776dbcde9b409eaaa6406fb50d42cfbf70ee8cb40d00be" } } ], "extra": [ 1, 31, 213, 90, 79, 211, 162, 125, 58, 97, 255, 22, 40, 203, 90, 74, 13, 216, 117, 20, 214, 220, 116, 170, 157, 28, 101, 94, 6, 159, 162, 98, 68, 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