Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d02ec46a86000ff0681203fd27c545c37a4bab2a1cd8c43e9e0b3df969d2545a

Tx prefix hash: 87a29c5935719269ec65685d658b4bddbd994836f0e49b21f99987100b9537ae
Tx public key: 94e65e3cce3b4eb3758b1e97780c794ef876032b0bc4d7aa2f87c66734ee94be
Timestamp: 1699906345 Timestamp [UCT]: 2023-11-13 20:12:25 Age [y:d:h:m:s]: 01:214:10:24:56
Block: 890969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414395 RingCT/type: yes/0
Extra: 0194e65e3cce3b4eb3758b1e97780c794ef876032b0bc4d7aa2f87c66734ee94be02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.685251257000 dcy

stealth address amount amount idx
00: fc8364e2e9a6fd07005d18cd4268a5d2f41778596adfcda00be6ff99829453da 0.685251257000 1347004 of 0

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": 890979, "vin": [ { "gen": { "height": 890969 } } ], "vout": [ { "amount": 685251257, "target": { "key": "fc8364e2e9a6fd07005d18cd4268a5d2f41778596adfcda00be6ff99829453da" } } ], "extra": [ 1, 148, 230, 94, 60, 206, 59, 78, 179, 117, 139, 30, 151, 120, 12, 121, 78, 248, 118, 3, 43, 11, 196, 215, 170, 47, 135, 198, 103, 52, 238, 148, 190, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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