Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273386d2b7ad2220d91b425ba0a89913bb67cc7c3b9329cd7a946db89158d1b9

Tx prefix hash: b390022fc0ac2a63eb89c7103a2a2bed19f896c750215b2bc28cf006cb4e5df9
Tx public key: 7e7eeb620d6b68dba99e786bee304bfec142ad93d8561c7f9cfc87f574462232
Timestamp: 1733529272 Timestamp [UCT]: 2024-12-06 23:54:32 Age [y:d:h:m:s]: 00:110:22:14:16
Block: 1169613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79071 RingCT/type: yes/0
Extra: 017e7eeb620d6b68dba99e786bee304bfec142ad93d8561c7f9cfc87f574462232021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6cc1ec5e20d9667f770a612cd0ab0aa5dd5de2b7f5f5c9d63c380ad61e9f32e 0.600000000000 1655334 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": 1169623, "vin": [ { "gen": { "height": 1169613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6cc1ec5e20d9667f770a612cd0ab0aa5dd5de2b7f5f5c9d63c380ad61e9f32e" } } ], "extra": [ 1, 126, 126, 235, 98, 13, 107, 104, 219, 169, 158, 120, 107, 238, 48, 75, 254, 193, 66, 173, 147, 216, 86, 28, 127, 156, 252, 135, 245, 116, 70, 34, 50, 2, 17, 0, 0, 0, 3, 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