Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b3a4b17f1d24f10c32132fb2fa8fe278d5a8cddd4fd8bf4217aa728692d58f

Tx prefix hash: b41f6f5bcba52ee43a9042e3d867f165204e38a2b676fe9a108afb431c642640
Tx public key: b59ca69ba11fc2e4b233f325bca6acc656450b527da7fa51c6afefdcf9119129
Timestamp: 1695650973 Timestamp [UCT]: 2023-09-25 14:09:33 Age [y:d:h:m:s]: 01:192:04:52:36
Block: 855890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398426 RingCT/type: yes/0
Extra: 01b59ca69ba11fc2e4b233f325bca6acc656450b527da7fa51c6afefdcf911912902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.895532149000 dcy

stealth address amount amount idx
00: 9970f10a44eb5a6aa83641fefe238e0e0319e690e3ec50eec0ee90a0bc2c16a0 0.895532149000 1309938 of 0

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": 855900, "vin": [ { "gen": { "height": 855890 } } ], "vout": [ { "amount": 895532149, "target": { "key": "9970f10a44eb5a6aa83641fefe238e0e0319e690e3ec50eec0ee90a0bc2c16a0" } } ], "extra": [ 1, 181, 156, 166, 155, 161, 31, 194, 228, 178, 51, 243, 37, 188, 166, 172, 198, 86, 69, 11, 82, 125, 167, 250, 81, 198, 175, 239, 220, 249, 17, 145, 41, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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