Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a4f5cd86a1dcbf00bf0cf5827fe6686b44ddf1ec2620d00bebf81dd07a60a86

Tx prefix hash: c81f12cb699524dab8d06df8152891960bcc8fd0e0d9b342d228ce6f455253e4
Tx public key: 0ab002c77707a9a1f4e918a453a85d16ad3a40ee74329965cf1b1c0a813d130a
Timestamp: 1684342559 Timestamp [UCT]: 2023-05-17 16:55:59 Age [y:d:h:m:s]: 02:016:17:03:55
Block: 762191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534072 RingCT/type: yes/0
Extra: 010ab002c77707a9a1f4e918a453a85d16ad3a40ee74329965cf1b1c0a813d130a021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.830395763000 dcy

stealth address amount amount idx
00: cc353305f59dc4000068f2fed0859970d3a397eea624940cee7bf114c8604213 1.830395763000 1210910 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": 762201, "vin": [ { "gen": { "height": 762191 } } ], "vout": [ { "amount": 1830395763, "target": { "key": "cc353305f59dc4000068f2fed0859970d3a397eea624940cee7bf114c8604213" } } ], "extra": [ 1, 10, 176, 2, 199, 119, 7, 169, 161, 244, 233, 24, 164, 83, 168, 93, 22, 173, 58, 64, 238, 116, 50, 153, 101, 207, 27, 28, 10, 129, 61, 19, 10, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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