Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01cd5759319657bb886dd469c1874b41f3e071e472281733a95a8c95aa8b026e

Tx prefix hash: 1cc3003d3e1901457a832a37adec7134393ff914a4e9d20d498183b9494afaba
Tx public key: b76cdd98f4bd705844cd6f225cbc9a999ce5f1cb8aacbd4a15eb504b85a510de
Timestamp: 1722404939 Timestamp [UCT]: 2024-07-31 05:48:59 Age [y:d:h:m:s]: 00:162:22:16:38
Block: 1077493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116564 RingCT/type: yes/0
Extra: 01b76cdd98f4bd705844cd6f225cbc9a999ce5f1cb8aacbd4a15eb504b85a510de0211000000038c7e50ca000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddb5b364e2d415f05afd65755c22fe9c364e46c7c784b6aea0bc6a330bd9cddb 0.600000000000 1550042 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": 1077503, "vin": [ { "gen": { "height": 1077493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddb5b364e2d415f05afd65755c22fe9c364e46c7c784b6aea0bc6a330bd9cddb" } } ], "extra": [ 1, 183, 108, 221, 152, 244, 189, 112, 88, 68, 205, 111, 34, 92, 188, 154, 153, 156, 229, 241, 203, 138, 172, 189, 74, 21, 235, 80, 75, 133, 165, 16, 222, 2, 17, 0, 0, 0, 3, 140, 126, 80, 202, 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