Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0fcb7a69bc15109bc8578d7f013cc7acfd875591fd44511d36366017fb9925f

Tx prefix hash: 49ba78db631b5fe69c36bd614578cc9cda4bdb7d48dbf6a24ea53a54080c20ff
Tx public key: 738f528dff0d13c9c2ef187f9bad1b38107a4a50bd71d28d4ef260a53537f110
Timestamp: 1749160992 Timestamp [UCT]: 2025-06-05 22:03:12 Age [y:d:h:m:s]: 00:168:00:24:08
Block: 1298759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117771 RingCT/type: yes/0
Extra: 01738f528dff0d13c9c2ef187f9bad1b38107a4a50bd71d28d4ef260a53537f110021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a27b6a9454f22b133431693cd4c6fda1ce45f85d31d77611f96a1b2ed914d9c2 0.600000000000 1786290 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": 1298769, "vin": [ { "gen": { "height": 1298759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27b6a9454f22b133431693cd4c6fda1ce45f85d31d77611f96a1b2ed914d9c2" } } ], "extra": [ 1, 115, 143, 82, 141, 255, 13, 19, 201, 194, 239, 24, 127, 155, 173, 27, 56, 16, 122, 74, 80, 189, 113, 210, 141, 78, 242, 96, 165, 53, 55, 241, 16, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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