Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84e1106b0cec7a31a30db7c31cf54cc7ea8ef3cb1e4526bb499e7e696f4a5f9c

Tx prefix hash: 9cffd4b7ac6e65c25793416fbf64125e85e0948db33d5ccc804c0abb25e43a9b
Tx public key: f80355f1cad437572199aca2ed9c6e92f914a65fd407fa8674a112f28474f216
Timestamp: 1700816453 Timestamp [UCT]: 2023-11-24 09:00:53 Age [y:d:h:m:s]: 01:151:07:49:21
Block: 898510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369328 RingCT/type: yes/0
Extra: 01f80355f1cad437572199aca2ed9c6e92f914a65fd407fa8674a112f28474f21602110000000433af99f4000000000000000000

1 output(s) for total of 0.646939050000 dcy

stealth address amount amount idx
00: 8c2a0b5352fe51958e277e97a6af40e1bec5122a09fb9558610a0153dda362c9 0.646939050000 1354931 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": 898520, "vin": [ { "gen": { "height": 898510 } } ], "vout": [ { "amount": 646939050, "target": { "key": "8c2a0b5352fe51958e277e97a6af40e1bec5122a09fb9558610a0153dda362c9" } } ], "extra": [ 1, 248, 3, 85, 241, 202, 212, 55, 87, 33, 153, 172, 162, 237, 156, 110, 146, 249, 20, 166, 95, 212, 7, 250, 134, 116, 161, 18, 242, 132, 116, 242, 22, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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