Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbab72b11dcfcb4514ec1e5c5eba37d37d4ea4fb23395145a00af4daab92f558

Tx prefix hash: 590ea0f8583a0dba9adb7bba1360d5ef4019e259213bf073f39a3ecc95afae24
Tx public key: b429f24dd9b4cb6609b6a21a56dfada98395c844c73c081fa126d396eb252d04
Timestamp: 1732737811 Timestamp [UCT]: 2024-11-27 20:03:31 Age [y:d:h:m:s]: 00:130:06:55:39
Block: 1163052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92917 RingCT/type: yes/0
Extra: 01b429f24dd9b4cb6609b6a21a56dfada98395c844c73c081fa126d396eb252d04021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20ba0a5e20bf79ffe5ac811f2cf6f94d5e70dc99de5293fe975d5e328ce3aca2 0.600000000000 1648717 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": 1163062, "vin": [ { "gen": { "height": 1163052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20ba0a5e20bf79ffe5ac811f2cf6f94d5e70dc99de5293fe975d5e328ce3aca2" } } ], "extra": [ 1, 180, 41, 242, 77, 217, 180, 203, 102, 9, 182, 162, 26, 86, 223, 173, 169, 131, 149, 200, 68, 199, 60, 8, 31, 161, 38, 211, 150, 235, 37, 45, 4, 2, 17, 0, 0, 0, 1, 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