Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b886bb22bc3d9508854b721d52e0f86bfe5fa7a57825b19209bece35be6220cb

Tx prefix hash: 0f4e55e37613bd0812496516d8fa91a147611122472c1896f4b5f1a6b3d30a2d
Tx public key: 1a43b7bf86f3d3e1ae858ec184da0ea6467cf43122541c86bd9b82a43d351b9e
Timestamp: 1729168737 Timestamp [UCT]: 2024-10-17 12:38:57 Age [y:d:h:m:s]: 00:073:05:25:49
Block: 1133568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52318 RingCT/type: yes/0
Extra: 011a43b7bf86f3d3e1ae858ec184da0ea6467cf43122541c86bd9b82a43d351b9e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20c0db9a5ec49d5c6dfb8dc7797938555d5dd14ab79496943e589fc92002b61b 0.600000000000 1616727 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": 1133578, "vin": [ { "gen": { "height": 1133568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20c0db9a5ec49d5c6dfb8dc7797938555d5dd14ab79496943e589fc92002b61b" } } ], "extra": [ 1, 26, 67, 183, 191, 134, 243, 211, 225, 174, 133, 142, 193, 132, 218, 14, 166, 70, 124, 244, 49, 34, 84, 28, 134, 189, 155, 130, 164, 61, 53, 27, 158, 2, 17, 0, 0, 0, 2, 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