Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ab3a2365c177bfd58850961c70f365878090fa2aba038753d8539383ee7af19

Tx prefix hash: cbd1cf3da30b8ef3ed048e8afbdd68676685f0561150bf35e9c3982b5de7d39d
Tx public key: cf8b3a3be8951ff0fd2919ffab0b7d3f399bf69256cec49122c0a3cdffb8112a
Timestamp: 1578161955 Timestamp [UCT]: 2020-01-04 18:19:15 Age [y:d:h:m:s]: 04:360:00:05:32
Block: 38716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146463 RingCT/type: yes/0
Extra: 01cf8b3a3be8951ff0fd2919ffab0b7d3f399bf69256cec49122c0a3cdffb8112a021100000005d81c26c0000000000000000000

1 output(s) for total of 456.800069772000 dcy

stealth address amount amount idx
00: 15732cece92382fb2108459e23fcda834f5470c85b0b85a30c5ee30db5272939 456.800069772000 66212 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": 38726, "vin": [ { "gen": { "height": 38716 } } ], "vout": [ { "amount": 456800069772, "target": { "key": "15732cece92382fb2108459e23fcda834f5470c85b0b85a30c5ee30db5272939" } } ], "extra": [ 1, 207, 139, 58, 59, 232, 149, 31, 240, 253, 41, 25, 255, 171, 11, 125, 63, 57, 155, 246, 146, 86, 206, 196, 145, 34, 192, 163, 205, 255, 184, 17, 42, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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