Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89cb3cf61807416551ce2c0fc94b7f8b5c7804e59c2e150fd233dba9e93a5051

Tx prefix hash: d49116f5b5e4970f5adbf65b7791baf447dd31e005b49d5069c3330ce3bf7141
Tx public key: 66b79e5d653e9bb20b44e84de0661d7c9035ada897592507fa3323f8a4bf6ead
Timestamp: 1728884207 Timestamp [UCT]: 2024-10-14 05:36:47 Age [y:d:h:m:s]: 00:100:08:18:06
Block: 1131216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71684 RingCT/type: yes/0
Extra: 0166b79e5d653e9bb20b44e84de0661d7c9035ada897592507fa3323f8a4bf6ead021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5b1e5974693fcfab97d94d6b93619d1eade82db6fe0a951fd7d193a287a4ed6 0.600000000000 1614097 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": 1131226, "vin": [ { "gen": { "height": 1131216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5b1e5974693fcfab97d94d6b93619d1eade82db6fe0a951fd7d193a287a4ed6" } } ], "extra": [ 1, 102, 183, 158, 93, 101, 62, 155, 178, 11, 68, 232, 77, 224, 102, 29, 124, 144, 53, 173, 168, 151, 89, 37, 7, 250, 51, 35, 248, 164, 191, 110, 173, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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