Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bc0098a1176ab4a52d3e55ff8697a8115d6d800beb096fac6fec84d069392bd

Tx prefix hash: 5800aa3b4eb46e72108daef8d2b56ec263b2ee4907e33d3b62a25b149c3acf7d
Tx public key: bbd16a7cc704e8bb6aaac596aeab6bceff4989c68ac03e42094227ae47d68e84
Timestamp: 1714332048 Timestamp [UCT]: 2024-04-28 19:20:48 Age [y:d:h:m:s]: 00:256:17:57:46
Block: 1010556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183775 RingCT/type: yes/0
Extra: 01bbd16a7cc704e8bb6aaac596aeab6bceff4989c68ac03e42094227ae47d68e8402110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f43d35c120a1325822694b9b3ea6be5a298d1377d40f2bb611806974141a13e 0.600000000000 1472546 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": 1010566, "vin": [ { "gen": { "height": 1010556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f43d35c120a1325822694b9b3ea6be5a298d1377d40f2bb611806974141a13e" } } ], "extra": [ 1, 187, 209, 106, 124, 199, 4, 232, 187, 106, 170, 197, 150, 174, 171, 107, 206, 255, 73, 137, 198, 138, 192, 62, 66, 9, 66, 39, 174, 71, 214, 142, 132, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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