Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d9d65d7191fea159a69382513dc1f20ec7d98bebc289db96fb083c736b64b36

Tx prefix hash: 1d459ca450479d542baa5e957a9eb0020054eebc5312cc702ac85827f3a9c9c9
Tx public key: 6b1a6d9b7b0fa8bccac4f8a136a52672ef791b35cad4fabef23829e0221d4af0
Timestamp: 1737636306 Timestamp [UCT]: 2025-01-23 12:45:06 Age [y:d:h:m:s]: 00:144:19:06:47
Block: 1203577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103230 RingCT/type: yes/0
Extra: 016b1a6d9b7b0fa8bccac4f8a136a52672ef791b35cad4fabef23829e0221d4af0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30bbc2f7150a93bece4115826f4c5e69e0e795243c4f81fc9427ee575179671 0.600000000000 1690254 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": 1203587, "vin": [ { "gen": { "height": 1203577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30bbc2f7150a93bece4115826f4c5e69e0e795243c4f81fc9427ee575179671" } } ], "extra": [ 1, 107, 26, 109, 155, 123, 15, 168, 188, 202, 196, 248, 161, 54, 165, 38, 114, 239, 121, 27, 53, 202, 212, 250, 190, 242, 56, 41, 224, 34, 29, 74, 240, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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