Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1ebf22c57d1c8e0196b9dc180d1daef20a9030c458abd1ec8cc8df12de8f3d

Tx prefix hash: 61b9a1614fdeffaff426f53d115222d571ba0fe9f01b6a3cf87959190ffa8080
Tx public key: 65596feb4a133f8d0cdfbe7b9394a434c0055192470595a7001b92ea45677c35
Timestamp: 1712666823 Timestamp [UTC]: 2024-04-09 12:47:03 Age [y:d:h:m:s]: 01:311:11:12:25
Block: 996737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481227 RingCT/type: yes/0
Extra: 0165596feb4a133f8d0cdfbe7b9394a434c0055192470595a7001b92ea45677c350211000000080011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a813c4efcef3fbc184c7585911f8a00734fa7508683f99af35dbadaa85f3a095 0.000600000000 1457163 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 dinastycoin-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": 996747, "vin": [ { "gen": { "height": 996737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a813c4efcef3fbc184c7585911f8a00734fa7508683f99af35dbadaa85f3a095" } } ], "extra": [ 1, 101, 89, 111, 235, 74, 19, 63, 141, 12, 223, 190, 123, 147, 148, 164, 52, 192, 5, 81, 146, 71, 5, 149, 167, 0, 27, 146, 234, 69, 103, 124, 53, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369