Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161fb674ab8e74ae24fddf3e73c82d97e9ff541083eae818bc785d6add06aa06

Tx prefix hash: c2919df541a4c0045c7bbe8e0c405db34de80be2d0455af9fdfa6e2454be4384
Tx public key: 98131992186ed9becf7ed2dc61fb288f73a4a06f889f7c9fcfaa500f75e302e4
Timestamp: 1731773673 Timestamp [UCT]: 2024-11-16 16:14:33 Age [y:d:h:m:s]: 00:137:11:18:06
Block: 1155061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98068 RingCT/type: yes/0
Extra: 0198131992186ed9becf7ed2dc61fb288f73a4a06f889f7c9fcfaa500f75e302e40211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9f37c94b30f561f1d85a6699dfeed7831910ab5c4fee452b29ae58f4ee13204 0.600000000000 1640674 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": 1155071, "vin": [ { "gen": { "height": 1155061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f37c94b30f561f1d85a6699dfeed7831910ab5c4fee452b29ae58f4ee13204" } } ], "extra": [ 1, 152, 19, 25, 146, 24, 110, 217, 190, 207, 126, 210, 220, 97, 251, 40, 143, 115, 164, 160, 111, 136, 159, 124, 159, 207, 170, 80, 15, 117, 227, 2, 228, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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