Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5561c69548be074489edf396936d64d383b7cb67db4b566a0a2d9c2a6dcd06a7

Tx prefix hash: 9aafc628e55a40554076058a8ae7a1cedcc5cde56de30463b07a6be99b5ebd68
Tx public key: 2a89d2c98b611fd24a28923ee16539f8a70b1a48872efbf600201a9ac969d431
Timestamp: 1718863638 Timestamp [UCT]: 2024-06-20 06:07:18 Age [y:d:h:m:s]: 01:143:14:22:00
Block: 1048137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361179 RingCT/type: yes/0
Extra: 012a89d2c98b611fd24a28923ee16539f8a70b1a48872efbf600201a9ac969d43102110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb2abaa33b9ea4429e77a737ebc1f04fc0b553e974fd707a3be256f4f87d4dc0 0.600000000000 1518144 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": 1048147, "vin": [ { "gen": { "height": 1048137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb2abaa33b9ea4429e77a737ebc1f04fc0b553e974fd707a3be256f4f87d4dc0" } } ], "extra": [ 1, 42, 137, 210, 201, 139, 97, 31, 210, 74, 40, 146, 62, 225, 101, 57, 248, 167, 11, 26, 72, 135, 46, 251, 246, 0, 32, 26, 154, 201, 105, 212, 49, 2, 17, 0, 0, 0, 16, 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