Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c0c512472470646b3d3e65ac83a9fb37f1fe407793b0d6c1959c8fd3947af6d

Tx prefix hash: a00985625a393ee7963e87128993d45319038db06c796b2fbeaa77a4dcd366f1
Tx public key: 2bdfff701a39c8a0f415a5fdde6c3f5af39b72aea3e231bed79955004ef48e5e
Timestamp: 1734131454 Timestamp [UCT]: 2024-12-13 23:10:54 Age [y:d:h:m:s]: 00:026:23:54:00
Block: 1174610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19304 RingCT/type: yes/0
Extra: 012bdfff701a39c8a0f415a5fdde6c3f5af39b72aea3e231bed79955004ef48e5e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 491d2a37c73c39e864530b84811da849e74af8902b4171399b695b8814241962 0.600000000000 1660787 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": 1174620, "vin": [ { "gen": { "height": 1174610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "491d2a37c73c39e864530b84811da849e74af8902b4171399b695b8814241962" } } ], "extra": [ 1, 43, 223, 255, 112, 26, 57, 200, 160, 244, 21, 165, 253, 222, 108, 63, 90, 243, 155, 114, 174, 163, 226, 49, 190, 215, 153, 85, 0, 78, 244, 142, 94, 2, 17, 0, 0, 0, 4, 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