Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 286f709be5b9546f10f62e2305e10581a3c4834d3a733a944f101f7c05a3d986

Tx prefix hash: f024ba982e6819dafc39b1aec651204650293518640b134d97d2e199b973ccde
Tx public key: e36fa56da1ba741a3e764d0e9fb804c1c1939a7514c463f663ff9cf7ab97c022
Timestamp: 1737058235 Timestamp [UCT]: 2025-01-16 20:10:35 Age [y:d:h:m:s]: 00:151:19:45:56
Block: 1198828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108222 RingCT/type: yes/0
Extra: 01e36fa56da1ba741a3e764d0e9fb804c1c1939a7514c463f663ff9cf7ab97c022021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dba100e6d9cb0edf4dee01405f5dded8b74f4d6ad4f8a28d2d9b474c749626f6 0.600000000000 1685455 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": 1198838, "vin": [ { "gen": { "height": 1198828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dba100e6d9cb0edf4dee01405f5dded8b74f4d6ad4f8a28d2d9b474c749626f6" } } ], "extra": [ 1, 227, 111, 165, 109, 161, 186, 116, 26, 62, 118, 77, 14, 159, 184, 4, 193, 193, 147, 154, 117, 20, 196, 99, 246, 99, 255, 156, 247, 171, 151, 192, 34, 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