Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660c94fc2861597bf69247692f78b7ef90573171db4c60d65c380e2e3300808a

Tx prefix hash: 7433e4f6d97dc1b4ce6f1c12f3c2dd26485ef171510ec3f1b546a57617ed30d6
Tx public key: 17c03d3ba384da24f1ebc82a3bb80b7e93508143d5dfa1f674d37a31061fefd4
Timestamp: 1707306363 Timestamp [UCT]: 2024-02-07 11:46:03 Age [y:d:h:m:s]: 00:336:19:39:09
Block: 952314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241129 RingCT/type: yes/0
Extra: 0117c03d3ba384da24f1ebc82a3bb80b7e93508143d5dfa1f674d37a31061fefd402110000001610a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfa8af44cbb82744e1c1e13f21be2fdb0749e2ba3f046e42d91128d98081499f 0.600000000000 1411234 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": 952324, "vin": [ { "gen": { "height": 952314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfa8af44cbb82744e1c1e13f21be2fdb0749e2ba3f046e42d91128d98081499f" } } ], "extra": [ 1, 23, 192, 61, 59, 163, 132, 218, 36, 241, 235, 200, 42, 59, 184, 11, 126, 147, 80, 129, 67, 213, 223, 161, 246, 116, 211, 122, 49, 6, 31, 239, 212, 2, 17, 0, 0, 0, 22, 16, 161, 116, 143, 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