Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c573177af416fc9a398b051e06e34d6273ca0433024586c2b8588727b0b87fe9

Tx prefix hash: 74184bfbb9cc58078a57e6d2f0a8c6faf8d41666d29b17fbe749c617fc74fd72
Tx public key: f0c54def59c187d52f6c304f3951e85837c95003153d6e021719ffc9224f76fd
Timestamp: 1697400048 Timestamp [UCT]: 2023-10-15 20:00:48 Age [y:d:h:m:s]: 01:210:00:31:04
Block: 870389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411154 RingCT/type: yes/0
Extra: 01f0c54def59c187d52f6c304f3951e85837c95003153d6e021719ffc9224f76fd021100000005faf35c9c000000000000000000

1 output(s) for total of 0.801751819000 dcy

stealth address amount amount idx
00: 39a4c59bb0abf77bea120222acd00153216ca5c75b6f86888c44c51243f0d2e5 0.801751819000 1325268 of 0

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": 870399, "vin": [ { "gen": { "height": 870389 } } ], "vout": [ { "amount": 801751819, "target": { "key": "39a4c59bb0abf77bea120222acd00153216ca5c75b6f86888c44c51243f0d2e5" } } ], "extra": [ 1, 240, 197, 77, 239, 89, 193, 135, 213, 47, 108, 48, 79, 57, 81, 232, 88, 55, 201, 80, 3, 21, 61, 110, 2, 23, 25, 255, 201, 34, 79, 118, 253, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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