Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2da4818d61cd393e31f8bd79c58b0c6786a7d7652385a242b080002af8ae931b

Tx prefix hash: 4afa0624bc092046cebd6208dec4a6ef7bc6b207dd0817c944a6c3b6b0e831a4
Tx public key: 66e200d55ff4b8859d0c08544e2f24b37d7a29fc5acf7758e2aa25b02f32d15f
Timestamp: 1719582343 Timestamp [UCT]: 2024-06-28 13:45:43 Age [y:d:h:m:s]: 00:319:05:10:03
Block: 1054089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228131 RingCT/type: yes/0
Extra: 0166e200d55ff4b8859d0c08544e2f24b37d7a29fc5acf7758e2aa25b02f32d15f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c39bf7a97a3648389c336fbbc2807a2893a7915565d125dad93f33f74facf364 0.600000000000 1524448 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": 1054099, "vin": [ { "gen": { "height": 1054089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c39bf7a97a3648389c336fbbc2807a2893a7915565d125dad93f33f74facf364" } } ], "extra": [ 1, 102, 226, 0, 213, 95, 244, 184, 133, 157, 12, 8, 84, 78, 47, 36, 179, 125, 122, 41, 252, 90, 207, 119, 88, 226, 170, 37, 176, 47, 50, 209, 95, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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