Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d94db5bd5f25503e41e5ddca96185dfcdc35f679afece602af65164d9b9cf22

Tx prefix hash: e1280085d8ff0c2873d9f3866dab5048b35fbc35ca64b63bcc7d6de578833e90
Tx public key: 6ee1f2fae05694c9ba19e82f5aa1d46f76cd6f2e319edde3f8a23c9359d6be02
Timestamp: 1715988437 Timestamp [UCT]: 2024-05-17 23:27:17 Age [y:d:h:m:s]: 00:350:09:13:23
Block: 1024296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250463 RingCT/type: yes/0
Extra: 016ee1f2fae05694c9ba19e82f5aa1d46f76cd6f2e319edde3f8a23c9359d6be02021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b787af10a63959066bac596da4bca559c692e78ea38c62ca05ee6212fbcae7d2 0.600000000000 1489933 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": 1024306, "vin": [ { "gen": { "height": 1024296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b787af10a63959066bac596da4bca559c692e78ea38c62ca05ee6212fbcae7d2" } } ], "extra": [ 1, 110, 225, 242, 250, 224, 86, 148, 201, 186, 25, 232, 47, 90, 161, 212, 111, 118, 205, 111, 46, 49, 158, 221, 227, 248, 162, 60, 147, 89, 214, 190, 2, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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