Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b816661d25297caa85e339e335dbc16a3fe7dfd8311d2030dad3ddc3c66134

Tx prefix hash: ef53abb152b020d0b6dc0c29264bd9d52ec2f82565a94af60add23f532da8967
Tx public key: 56d60ea9553f82ccbad301c31a01e8a8d63f3ad753e584ca2400902b8d187ee3
Timestamp: 1700708263 Timestamp [UCT]: 2023-11-23 02:57:43 Age [y:d:h:m:s]: 01:146:04:41:41
Block: 897611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365660 RingCT/type: yes/0
Extra: 0156d60ea9553f82ccbad301c31a01e8a8d63f3ad753e584ca2400902b8d187ee302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.651391561000 dcy

stealth address amount amount idx
00: 9a1d6191db60d430a96054e2fe4b72ebc9010a978f222f08928396a6a1be82f2 0.651391561000 1353992 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": 897621, "vin": [ { "gen": { "height": 897611 } } ], "vout": [ { "amount": 651391561, "target": { "key": "9a1d6191db60d430a96054e2fe4b72ebc9010a978f222f08928396a6a1be82f2" } } ], "extra": [ 1, 86, 214, 14, 169, 85, 63, 130, 204, 186, 211, 1, 195, 26, 1, 232, 168, 214, 63, 58, 215, 83, 229, 132, 202, 36, 0, 144, 43, 141, 24, 126, 227, 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