Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3493d78f6e2be58b815eec9ced22abc9a03503f208c88c57a7cfce969a6e973b

Tx prefix hash: 386a88c3eadf3001e40c3c9566000dc390c29d2403b7e4500817ce789b12f80a
Tx public key: 78bb4cb4310f3aea1ce2dcd711778d5ecf603b673c0ffd12b5f5f3f32e92f445
Timestamp: 1648568999 Timestamp [UCT]: 2022-03-29 15:49:59 Age [y:d:h:m:s]: 02:234:18:49:32
Block: 468987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687354 RingCT/type: yes/0
Extra: 0178bb4cb4310f3aea1ce2dcd711778d5ecf603b673c0ffd12b5f5f3f32e92f445021100000004c9067537000000000000000000

1 output(s) for total of 17.142970956000 dcy

stealth address amount amount idx
00: e538fb2f2b1a4dc523ca5e23ac245a29db2b60038eab4dbe8807d8cdc661986a 17.142970956000 887825 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": 468997, "vin": [ { "gen": { "height": 468987 } } ], "vout": [ { "amount": 17142970956, "target": { "key": "e538fb2f2b1a4dc523ca5e23ac245a29db2b60038eab4dbe8807d8cdc661986a" } } ], "extra": [ 1, 120, 187, 76, 180, 49, 15, 58, 234, 28, 226, 220, 215, 17, 119, 141, 94, 207, 96, 59, 103, 60, 15, 253, 18, 181, 245, 243, 243, 46, 146, 244, 69, 2, 17, 0, 0, 0, 4, 201, 6, 117, 55, 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