Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f118f1ae2f142e7be71f8643d5372383b4173fe539143aae6fadf6c25280d3f

Tx prefix hash: 7fc0444d1ae223eadf6796a8335ce41ff83483331fabbb1c8c09471d75db2dfd
Tx public key: bbdbde065b0163603c607f5bcc2156d58ca587498f9de825d70b8f69aae047f2
Timestamp: 1711643758 Timestamp [UCT]: 2024-03-28 16:35:58 Age [y:d:h:m:s]: 00:334:18:27:46
Block: 988301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239302 RingCT/type: yes/0
Extra: 01bbdbde065b0163603c607f5bcc2156d58ca587498f9de825d70b8f69aae047f202110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8607da9053304b0dc778423f3f1e6436f0da82857d7df81ce3ef8a0ef8948f9a 0.600000000000 1448576 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": 988311, "vin": [ { "gen": { "height": 988301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8607da9053304b0dc778423f3f1e6436f0da82857d7df81ce3ef8a0ef8948f9a" } } ], "extra": [ 1, 187, 219, 222, 6, 91, 1, 99, 96, 60, 96, 127, 91, 204, 33, 86, 213, 140, 165, 135, 73, 143, 157, 232, 37, 215, 11, 143, 105, 170, 224, 71, 242, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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