Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07a32fd4806b14158906e23eba87d6bb248dc5a26e41fd810ee7b6d069db5f4a

Tx prefix hash: 768b51c0f65b4852a220edb680b71c4a795127b228933f2f1bf192262a370767
Tx public key: f96d4da3ee5656b59f4a603e9d3e81ec56d4c5dc87739d2d3b6d7fb8bca7c6f8
Timestamp: 1728206831 Timestamp [UCT]: 2024-10-06 09:27:11 Age [y:d:h:m:s]: 01:045:08:17:34
Block: 1125601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290788 RingCT/type: yes/0
Extra: 01f96d4da3ee5656b59f4a603e9d3e81ec56d4c5dc87739d2d3b6d7fb8bca7c6f8021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71e73271088623a505373dced90e98ff22a0e7e9bb9f47bd29fde3c472c61372 0.600000000000 1608352 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": 1125611, "vin": [ { "gen": { "height": 1125601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71e73271088623a505373dced90e98ff22a0e7e9bb9f47bd29fde3c472c61372" } } ], "extra": [ 1, 249, 109, 77, 163, 238, 86, 86, 181, 159, 74, 96, 62, 157, 62, 129, 236, 86, 212, 197, 220, 135, 115, 157, 45, 59, 109, 127, 184, 188, 167, 198, 248, 2, 17, 0, 0, 0, 1, 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