Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4014ab155ab38dddfa84ab77470120de7fc0e4bc2068d173b65f3c317e3419d

Tx prefix hash: 27a3b102cbef6b20e1b280c238f179276c45ccab2c032a8e55d597fec8a6f9e9
Tx public key: 2825b1d4e52868b600548e3e1d498731c1508e5376f821e84d2cfa5e187083e7
Timestamp: 1727629108 Timestamp [UCT]: 2024-09-29 16:58:28 Age [y:d:h:m:s]: 01:039:14:59:12
Block: 1120804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286712 RingCT/type: yes/0
Extra: 012825b1d4e52868b600548e3e1d498731c1508e5376f821e84d2cfa5e187083e702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6439c34fb02bfabacf6820263c2038237ed2c4f43ea117a70950f163ce0c8c4 0.600000000000 1602851 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": 1120814, "vin": [ { "gen": { "height": 1120804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6439c34fb02bfabacf6820263c2038237ed2c4f43ea117a70950f163ce0c8c4" } } ], "extra": [ 1, 40, 37, 177, 212, 229, 40, 104, 182, 0, 84, 142, 62, 29, 73, 135, 49, 193, 80, 142, 83, 118, 248, 33, 232, 77, 44, 250, 94, 24, 112, 131, 231, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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