Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f72a6f1e7d514ed2a4b42e88bb2d2b3f1a410f474a783f94643349a74cbed51

Tx prefix hash: 0bfbb193f0821b08aaf77d87a1f469a8469ba2ee60643229b810484303f03de7
Tx public key: f8037fc87f2cb2655a033b8446a20815a41a136127172553d73605840fbbfd2b
Timestamp: 1639282613 Timestamp [UCT]: 2021-12-12 04:16:53 Age [y:d:h:m:s]: 03:323:20:16:45
Block: 393658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1007916 RingCT/type: yes/0
Extra: 01f8037fc87f2cb2655a033b8446a20815a41a136127172553d73605840fbbfd2b021100000002117daff0000000000000000000

1 output(s) for total of 30.454255817000 dcy

stealth address amount amount idx
00: 47c6f01c827f0912e4887cbd2692dff2636a5ec500d771b899c715768c0f23f3 30.454255817000 790965 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": 393668, "vin": [ { "gen": { "height": 393658 } } ], "vout": [ { "amount": 30454255817, "target": { "key": "47c6f01c827f0912e4887cbd2692dff2636a5ec500d771b899c715768c0f23f3" } } ], "extra": [ 1, 248, 3, 127, 200, 127, 44, 178, 101, 90, 3, 59, 132, 70, 162, 8, 21, 164, 26, 19, 97, 39, 23, 37, 83, 215, 54, 5, 132, 15, 187, 253, 43, 2, 17, 0, 0, 0, 2, 17, 125, 175, 240, 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