Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 692cc50587d8e744df8955e581988a1f3baa58a1ef3ec4aef5dd1d42a46e70f1

Tx prefix hash: 989460940ee77b7c96d1b68d7b8981d676a4fc4f75ea5a41291f0e74b8dadf04
Tx public key: 73439934de9c631d3edaa894e78a93449417897d357616a1fa2504139a00661d
Timestamp: 1705746364 Timestamp [UCT]: 2024-01-20 10:26:04 Age [y:d:h:m:s]: 01:079:10:56:15
Block: 939357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317884 RingCT/type: yes/0
Extra: 0173439934de9c631d3edaa894e78a93449417897d357616a1fa2504139a00661d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 303a770f15d3b943d82cb002af686ba2c37a0df34f5ccfeca6f8a0a17e308f27 0.600000000000 1397457 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": 939367, "vin": [ { "gen": { "height": 939357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "303a770f15d3b943d82cb002af686ba2c37a0df34f5ccfeca6f8a0a17e308f27" } } ], "extra": [ 1, 115, 67, 153, 52, 222, 156, 99, 29, 62, 218, 168, 148, 231, 138, 147, 68, 148, 23, 137, 125, 53, 118, 22, 161, 250, 37, 4, 19, 154, 0, 102, 29, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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