Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 893dfde937d220bd67a97439228ed7c4f24be2ac8c6ed66bf36ed2ee1ebd0a1b

Tx prefix hash: 9b7258ee76f2fdde1808cd06c5ea4259558ea4813f7264fc51fae680df9eec7b
Tx public key: 61aea5d23f66939e239faa65c70bdfa59a7eb6d2310c743474d129e7bec309e3
Timestamp: 1702668483 Timestamp [UCT]: 2023-12-15 19:28:03 Age [y:d:h:m:s]: 01:330:09:41:27
Block: 913863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495001 RingCT/type: yes/0
Extra: 0161aea5d23f66939e239faa65c70bdfa59a7eb6d2310c743474d129e7bec309e302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4532871e6092a8a6228105f5f967938ed108732c64bf5bf49c60bfe6a1e4e479 0.600000000000 1371143 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": 913873, "vin": [ { "gen": { "height": 913863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4532871e6092a8a6228105f5f967938ed108732c64bf5bf49c60bfe6a1e4e479" } } ], "extra": [ 1, 97, 174, 165, 210, 63, 102, 147, 158, 35, 159, 170, 101, 199, 11, 223, 165, 154, 126, 182, 210, 49, 12, 116, 52, 116, 209, 41, 231, 190, 195, 9, 227, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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