Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf20d30fae4f3753f4ae9f30b846e3c6e25e9915858cb676ae7252e8038ac40

Tx prefix hash: 831b8565680265a777a197875278b5e03ca96896405ceabd3b40de44dfee7cbe
Tx public key: e36a5b13b7f0cfaea6b33501a18254bf4437bedd9488003c9a9117fa54fd141b
Timestamp: 1708327144 Timestamp [UCT]: 2024-02-19 07:19:04 Age [y:d:h:m:s]: 01:118:05:22:45
Block: 960786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345449 RingCT/type: yes/0
Extra: 01e36a5b13b7f0cfaea6b33501a18254bf4437bedd9488003c9a9117fa54fd141b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4238693c32bd2a987fedc08b44170b2c8c4a71c87e963284cd6d528383e39b0e 0.600000000000 1420373 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": 960796, "vin": [ { "gen": { "height": 960786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4238693c32bd2a987fedc08b44170b2c8c4a71c87e963284cd6d528383e39b0e" } } ], "extra": [ 1, 227, 106, 91, 19, 183, 240, 207, 174, 166, 179, 53, 1, 161, 130, 84, 191, 68, 55, 190, 221, 148, 136, 0, 60, 154, 145, 23, 250, 84, 253, 20, 27, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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