Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09009a54526115c1e1bf903edc64c1a298d1a1b0f738c005094a8c2a1dda1a49

Tx prefix hash: 4244da5809b342a71a76840d8de37d3d2eda5994a6b10cee5e0dde908ed20da3
Tx public key: 5d6aea9da68e7176d3102b631398af96cee82a62777d6bfb0a4a6452819c6392
Timestamp: 1720331077 Timestamp [UCT]: 2024-07-07 05:44:37 Age [y:d:h:m:s]: 00:184:05:24:55
Block: 1060300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131822 RingCT/type: yes/0
Extra: 015d6aea9da68e7176d3102b631398af96cee82a62777d6bfb0a4a6452819c639202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa94698cbddf8a02f00af9b5be4d999834911fa09d25bb0d04981ecc1f5b737 0.600000000000 1530771 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": 1060310, "vin": [ { "gen": { "height": 1060300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa94698cbddf8a02f00af9b5be4d999834911fa09d25bb0d04981ecc1f5b737" } } ], "extra": [ 1, 93, 106, 234, 157, 166, 142, 113, 118, 211, 16, 43, 99, 19, 152, 175, 150, 206, 232, 42, 98, 119, 125, 107, 251, 10, 74, 100, 82, 129, 156, 99, 146, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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