Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84cbb40087a52da22d9112157478e0ea1c4595f2a76a3b21e88f240a5d2e2ecf

Tx prefix hash: 5bf217bfd0339fc90b9c71234a167b88996ff0181a1e1b984550633bd3fbdc9a
Tx public key: 26baba3ad6fd1292dd9304d7d3f0d8f8b31cbfa97c7c05104052c1a147721c80
Timestamp: 1736029592 Timestamp [UCT]: 2025-01-04 22:26:32 Age [y:d:h:m:s]: 00:092:03:14:56
Block: 1190319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65616 RingCT/type: yes/0
Extra: 0126baba3ad6fd1292dd9304d7d3f0d8f8b31cbfa97c7c05104052c1a147721c80021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 179fd04722c4f3f99eec6e9b31cbb53770064934fc3d737836d44e4a095b5115 0.600000000000 1676834 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": 1190329, "vin": [ { "gen": { "height": 1190319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "179fd04722c4f3f99eec6e9b31cbb53770064934fc3d737836d44e4a095b5115" } } ], "extra": [ 1, 38, 186, 186, 58, 214, 253, 18, 146, 221, 147, 4, 215, 211, 240, 216, 248, 179, 28, 191, 169, 124, 124, 5, 16, 64, 82, 193, 161, 71, 114, 28, 128, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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