Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc2795128a52accef264f882778bd11ffa9b556e7af145b1fd5c1fee67d814ba

Tx prefix hash: 28da5fc1201d28246feb91ba19e5d7680c8a99cd4e208de438c188a1cd2cd037
Tx public key: 21aa5d3ec66f6e36bb2ae8a7820b623ffdc1d67b4b6ed6784fa69a45a1057ddd
Timestamp: 1733974880 Timestamp [UCT]: 2024-12-12 03:41:20 Age [y:d:h:m:s]: 00:119:08:15:31
Block: 1173324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85075 RingCT/type: yes/0
Extra: 0121aa5d3ec66f6e36bb2ae8a7820b623ffdc1d67b4b6ed6784fa69a45a1057ddd021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dac5be509385862e1626e09c400ddda25e3d78287a9f287bbf0137f606223358 0.600000000000 1659335 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": 1173334, "vin": [ { "gen": { "height": 1173324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dac5be509385862e1626e09c400ddda25e3d78287a9f287bbf0137f606223358" } } ], "extra": [ 1, 33, 170, 93, 62, 198, 111, 110, 54, 187, 42, 232, 167, 130, 11, 98, 63, 253, 193, 214, 123, 75, 110, 214, 120, 79, 166, 154, 69, 161, 5, 125, 221, 2, 17, 0, 0, 0, 5, 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