Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4394a2911c160ed7fdf31d6ea75d7603fc562040d44e2d1dc6b68df479cf27f3

Tx prefix hash: ed9525545c9d089cf5d3a3a26d9f0a5393cb88561556a855f222567e54070582
Tx public key: 9092e08b32759188c5830b311f6d840fdf9e44a5121c62fee29f41a3cbf289da
Timestamp: 1726296145 Timestamp [UCT]: 2024-09-14 06:42:25 Age [y:d:h:m:s]: 00:061:17:21:28
Block: 1109746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44135 RingCT/type: yes/0
Extra: 019092e08b32759188c5830b311f6d840fdf9e44a5121c62fee29f41a3cbf289da021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2857667ad932884085a1913cc80bcb02b5a76fe6f0909acbbe60c631d5eecb15 0.600000000000 1588113 of 15

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": 1109756, "vin": [ { "gen": { "height": 1109746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2857667ad932884085a1913cc80bcb02b5a76fe6f0909acbbe60c631d5eecb15" } } ], "extra": [ 1, 144, 146, 224, 139, 50, 117, 145, 136, 197, 131, 11, 49, 31, 109, 132, 15, 223, 158, 68, 165, 18, 28, 98, 254, 226, 159, 65, 163, 203, 242, 137, 218, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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