Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98825ad98e6d04d779dd854e3860f2f18bd5ce7796e6dc0ed542ee96f9bfa3d2

Tx prefix hash: cb96ea2019121de96b9f3b09a43ee19d86d4ffaa219c8876211cbb513dc43003
Tx public key: 57c846a70965f2bb6b1998f1c79fc9c7550df3ddaf379914033b55b7b231d8c6
Timestamp: 1675088694 Timestamp [UCT]: 2023-01-30 14:24:54 Age [y:d:h:m:s]: 02:066:18:18:01
Block: 686091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569350 RingCT/type: yes/0
Extra: 0157c846a70965f2bb6b1998f1c79fc9c7550df3ddaf379914033b55b7b231d8c602110000000175e3f0e9000000000000000000

1 output(s) for total of 3.271113706000 dcy

stealth address amount amount idx
00: 3eba5787cc48c9dd0b619bb015dc6e7d3df4b2a25cbe0d3a09c7db1af2b2ce2f 3.271113706000 1128556 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": 686101, "vin": [ { "gen": { "height": 686091 } } ], "vout": [ { "amount": 3271113706, "target": { "key": "3eba5787cc48c9dd0b619bb015dc6e7d3df4b2a25cbe0d3a09c7db1af2b2ce2f" } } ], "extra": [ 1, 87, 200, 70, 167, 9, 101, 242, 187, 107, 25, 152, 241, 199, 159, 201, 199, 85, 13, 243, 221, 175, 55, 153, 20, 3, 59, 85, 183, 178, 49, 216, 198, 2, 17, 0, 0, 0, 1, 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