Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6f056f2480a7b05d2d42796bac103aa8bc4150d35e3aefa950236de669a1283

Tx prefix hash: 134b865ed414b7a2d6952e29f5c187e88d16f3dc6dea2978bb75874670fcb8c7
Tx public key: b4a332a7d623c93d02fa81277040d8554fec019cb54cba9426e27c80a93b018d
Timestamp: 1713140683 Timestamp [UCT]: 2024-04-15 00:24:43 Age [y:d:h:m:s]: 00:360:10:24:51
Block: 1000665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257703 RingCT/type: yes/0
Extra: 01b4a332a7d623c93d02fa81277040d8554fec019cb54cba9426e27c80a93b018d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b4a14c31c640b0424a3013d0b3688d5948cf2302ba27f49f2d6ada2b793c7a5 0.600000000000 1461163 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": 1000675, "vin": [ { "gen": { "height": 1000665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b4a14c31c640b0424a3013d0b3688d5948cf2302ba27f49f2d6ada2b793c7a5" } } ], "extra": [ 1, 180, 163, 50, 167, 214, 35, 201, 61, 2, 250, 129, 39, 112, 64, 216, 85, 79, 236, 1, 156, 181, 76, 186, 148, 38, 226, 124, 128, 169, 59, 1, 141, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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