Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04c5209ed769afc24f9cbb63720c3a96b30bb3daeff47f948a1deddeabcc49f4

Tx prefix hash: 679c967540b7ba4dd96ca6cf59f485de328f1d7711b70e625310f09421d19f12
Tx public key: f0f22332055f92affac0d3ff76561f6a78cfb3a62c222d8e7fd98db0ae3483e5
Timestamp: 1715184850 Timestamp [UCT]: 2024-05-08 16:14:10 Age [y:d:h:m:s]: 00:363:06:10:37
Block: 1017650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259658 RingCT/type: yes/0
Extra: 01f0f22332055f92affac0d3ff76561f6a78cfb3a62c222d8e7fd98db0ae3483e502110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eb96e451d37a73f489071bd17fe22e9560bca1be3928a5c4ab46dff965a082a 0.600000000000 1481433 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": 1017660, "vin": [ { "gen": { "height": 1017650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eb96e451d37a73f489071bd17fe22e9560bca1be3928a5c4ab46dff965a082a" } } ], "extra": [ 1, 240, 242, 35, 50, 5, 95, 146, 175, 250, 192, 211, 255, 118, 86, 31, 106, 120, 207, 179, 166, 44, 34, 45, 142, 127, 217, 141, 176, 174, 52, 131, 229, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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