Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a78d8ddb0c5cfadffe0b0d62a0a406e1e73aa9b5ce391f60a305ba5531df3787

Tx prefix hash: 3cbbe9ee7b769bc77a83df370554597ba3e30d4ff8e7a740d21229c018444f7c
Tx public key: c9e192daa5ea288a29ecc0fe2c4292b850ca09caff2df50b20523b75c9369d82
Timestamp: 1739245701 Timestamp [UCT]: 2025-02-11 03:48:21 Age [y:d:h:m:s]: 00:239:03:57:58
Block: 1216674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168629 RingCT/type: yes/0
Extra: 01c9e192daa5ea288a29ecc0fe2c4292b850ca09caff2df50b20523b75c9369d82021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feca189a182c62a8852af74c0a3e473cc3b2c98f596a631c9e5ee65589546126 0.600000000000 1703481 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": 1216684, "vin": [ { "gen": { "height": 1216674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feca189a182c62a8852af74c0a3e473cc3b2c98f596a631c9e5ee65589546126" } } ], "extra": [ 1, 201, 225, 146, 218, 165, 234, 40, 138, 41, 236, 192, 254, 44, 66, 146, 184, 80, 202, 9, 202, 255, 45, 245, 11, 32, 82, 59, 117, 201, 54, 157, 130, 2, 17, 0, 0, 0, 1, 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