Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2d406950ed9a6c193eb96e7604e125e64bcd685d7c6850d31f0b48574c0084

Tx prefix hash: 7076f9f08e0716ab07bac8e801993b3ed6df9f9a4a4fadc08124641d9022b3f9
Tx public key: d3d120752f179a0ddc9a9a6c0713789b3bf8c0b9bff45eff50629ffe02add804
Timestamp: 1721442417 Timestamp [UCT]: 2024-07-20 02:26:57 Age [y:d:h:m:s]: 00:191:17:24:10
Block: 1069556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136881 RingCT/type: yes/0
Extra: 01d3d120752f179a0ddc9a9a6c0713789b3bf8c0b9bff45eff50629ffe02add804021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f14aa4eca67c7b3aa08bbe98baed5ba6462300585c9bf150d944eaeed64d77d 0.600000000000 1541017 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": 1069566, "vin": [ { "gen": { "height": 1069556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f14aa4eca67c7b3aa08bbe98baed5ba6462300585c9bf150d944eaeed64d77d" } } ], "extra": [ 1, 211, 209, 32, 117, 47, 23, 154, 13, 220, 154, 154, 108, 7, 19, 120, 155, 59, 248, 192, 185, 191, 244, 94, 255, 80, 98, 159, 254, 2, 173, 216, 4, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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