Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 490926597f6d79230f477db589c8793c3a3b6824acf1eec654d687f12575f127

Tx prefix hash: 9bf07d87aeb9e324bcb5502a24429fd01974c94c07779dd3b49e5dae358d335b
Tx public key: 04b3707df4b1ea926152ed2ed1c4ddb3f8b6ab1ae7963925646fa4b216cdd396
Timestamp: 1674825998 Timestamp [UCT]: 2023-01-27 13:26:38 Age [y:d:h:m:s]: 01:302:22:29:33
Block: 683917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477466 RingCT/type: yes/0
Extra: 0104b3707df4b1ea926152ed2ed1c4ddb3f8b6ab1ae7963925646fa4b216cdd3960211000000015029cbac000000000000000000

1 output(s) for total of 3.325822050000 dcy

stealth address amount amount idx
00: ff31898feab11a1cf0adc906cc6dffee6254ccbb26ce71458fae9fd68dd27eff 3.325822050000 1126122 of 0

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": 683927, "vin": [ { "gen": { "height": 683917 } } ], "vout": [ { "amount": 3325822050, "target": { "key": "ff31898feab11a1cf0adc906cc6dffee6254ccbb26ce71458fae9fd68dd27eff" } } ], "extra": [ 1, 4, 179, 112, 125, 244, 177, 234, 146, 97, 82, 237, 46, 209, 196, 221, 179, 248, 182, 171, 26, 231, 150, 57, 37, 100, 111, 164, 178, 22, 205, 211, 150, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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