Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b27653680609da617aa163dbc67af73886392f23bc6cc53f2bce36c987e4fb3

Tx prefix hash: 613c25a6d1d0496f361e562b9a86d83743ffdcb75ea428e9b92594a7f9e15234
Tx public key: 795f25f2cdc093f382baa4d0913b1cf140a190b1235f9b504f89c144d4cdface
Timestamp: 1735407524 Timestamp [UCT]: 2024-12-28 17:38:44 Age [y:d:h:m:s]: 00:172:18:38:58
Block: 1185160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123176 RingCT/type: yes/0
Extra: 01795f25f2cdc093f382baa4d0913b1cf140a190b1235f9b504f89c144d4cdface0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 535aace305b3d0b121423665e591ef9f8d67d5468bdc3c2bb77b64015ea48f35 0.600000000000 1671625 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": 1185170, "vin": [ { "gen": { "height": 1185160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "535aace305b3d0b121423665e591ef9f8d67d5468bdc3c2bb77b64015ea48f35" } } ], "extra": [ 1, 121, 95, 37, 242, 205, 192, 147, 243, 130, 186, 164, 208, 145, 59, 28, 241, 64, 161, 144, 177, 35, 95, 155, 80, 79, 137, 193, 68, 212, 205, 250, 206, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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