Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ca6830b64405c4eb639cfbd9d4c4dd61d51399fdfff41c02d7873b4bcee871c

Tx prefix hash: b6288394da8ec0abc2a1761d31212e2c8dc8eaf89f8bcb7fc622e7798b021466
Tx public key: 27bdf06baa92774b33553d18e6b89ece291607c70ea734c12de4707fe2ff1e4e
Timestamp: 1762930287 Timestamp [UCT]: 2025-11-12 06:51:27 Age [y:d:h:m:s]: 00:078:06:07:19
Block: 1410340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55853 RingCT/type: yes/0
Extra: 0127bdf06baa92774b33553d18e6b89ece291607c70ea734c12de4707fe2ff1e4e021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b051c6fb1f31fed19071f523bf87c51fb4120ba53fb02e19aa8a075134570435 0.600000000000 1898791 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": 1410350, "vin": [ { "gen": { "height": 1410340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b051c6fb1f31fed19071f523bf87c51fb4120ba53fb02e19aa8a075134570435" } } ], "extra": [ 1, 39, 189, 240, 107, 170, 146, 119, 75, 51, 85, 61, 24, 230, 184, 158, 206, 41, 22, 7, 199, 14, 167, 52, 193, 45, 228, 112, 127, 226, 255, 30, 78, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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