Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b142ed3019259fb4070e6f53bf2331220dafce07e063e4b620bd748c0912faf9

Tx prefix hash: 2e88882d261f603982e8389fe7409d0fecdf3263547e705fa068e2789739c3f9
Tx public key: 72df51aa0d552075225f0efadd9c79612865e55f3233fd58c57ffb3a30f8c05c
Timestamp: 1751074046 Timestamp [UCT]: 2025-06-28 01:27:26 Age [y:d:h:m:s]: 00:141:01:00:44
Block: 1314187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98892 RingCT/type: yes/0
Extra: 0172df51aa0d552075225f0efadd9c79612865e55f3233fd58c57ffb3a30f8c05c02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c4ee425f1b24ab04d7b613df425e4b446f5cc69e47b0650ba336a5eb110327 0.600000000000 1801832 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": 1314197, "vin": [ { "gen": { "height": 1314187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c4ee425f1b24ab04d7b613df425e4b446f5cc69e47b0650ba336a5eb110327" } } ], "extra": [ 1, 114, 223, 81, 170, 13, 85, 32, 117, 34, 95, 14, 250, 221, 156, 121, 97, 40, 101, 229, 95, 50, 51, 253, 88, 197, 127, 251, 58, 48, 248, 192, 92, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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