Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7da44379d7089f19f7b8e385a85f583784a6dc6ba47444ea08457f27af9404

Tx prefix hash: adc0ccb5b55036089d1a9960a66c986ea83b9d6c23b2ba27dc6e5770f765beb5
Tx public key: af75e9e8d8a36622237f87877df683105f1da5f3670171185469e41ea97cd4c0
Timestamp: 1725014138 Timestamp [UCT]: 2024-08-30 10:35:38 Age [y:d:h:m:s]: 00:214:20:41:30
Block: 1099126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153401 RingCT/type: yes/0
Extra: 01af75e9e8d8a36622237f87877df683105f1da5f3670171185469e41ea97cd4c002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36066002d72e45c1f4ff6f4cadf961e045560514e343b5a8b9af4d40b61895f5 0.600000000000 1575053 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": 1099136, "vin": [ { "gen": { "height": 1099126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36066002d72e45c1f4ff6f4cadf961e045560514e343b5a8b9af4d40b61895f5" } } ], "extra": [ 1, 175, 117, 233, 232, 216, 163, 102, 34, 35, 127, 135, 135, 125, 246, 131, 16, 95, 29, 165, 243, 103, 1, 113, 24, 84, 105, 228, 30, 169, 124, 212, 192, 2, 17, 0, 0, 0, 1, 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