Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9fd57c6025dca7ee29d3f56803f2a67a4accaf8131a5ab88d17c9ddf5ce59a

Tx prefix hash: 0038e88d514f84e2af253a9153734a45a75226178e76cff6dbe0ae556eb2ec90
Tx public key: 1f3437283802b6ddb5583c1f37468779f8393f55bb1ca302f86fe8dbe2425b11
Timestamp: 1714985220 Timestamp [UCT]: 2024-05-06 08:47:00 Age [y:d:h:m:s]: 00:342:21:13:09
Block: 1015981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245118 RingCT/type: yes/0
Extra: 011f3437283802b6ddb5583c1f37468779f8393f55bb1ca302f86fe8dbe2425b110211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4f630a474bf4d8892c4b9b515d8764653c643f5d214dc50c179d619d5583ef9 0.600000000000 1479436 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": 1015991, "vin": [ { "gen": { "height": 1015981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f630a474bf4d8892c4b9b515d8764653c643f5d214dc50c179d619d5583ef9" } } ], "extra": [ 1, 31, 52, 55, 40, 56, 2, 182, 221, 181, 88, 60, 31, 55, 70, 135, 121, 248, 57, 63, 85, 187, 28, 163, 2, 248, 111, 232, 219, 226, 66, 91, 17, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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