Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc0a0be79c2a4f34c82539e510ecc870125a65add88b9a2b8c5ef6b8b613dd0

Tx prefix hash: 54986446371127ac74d75786c29774c08442d5b3b3cffe05bda4b367573fb39d
Tx public key: fa45c3eab2d977e069e90771c6bfc40fd9b31fd63e13fdc0164c6c0945d725bc
Timestamp: 1737635709 Timestamp [UCT]: 2025-01-23 12:35:09 Age [y:d:h:m:s]: 00:301:14:34:44
Block: 1203570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213092 RingCT/type: yes/0
Extra: 01fa45c3eab2d977e069e90771c6bfc40fd9b31fd63e13fdc0164c6c0945d725bc021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3bce7a03839a8411f0152259f86c755223147431d14fbe3c61bb3844b55f6a5 0.600000000000 1690247 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": 1203580, "vin": [ { "gen": { "height": 1203570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3bce7a03839a8411f0152259f86c755223147431d14fbe3c61bb3844b55f6a5" } } ], "extra": [ 1, 250, 69, 195, 234, 178, 217, 119, 224, 105, 233, 7, 113, 198, 191, 196, 15, 217, 179, 31, 214, 62, 19, 253, 192, 22, 76, 108, 9, 69, 215, 37, 188, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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