Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f7a0d89701b0da450212e62343bcdecfb4413f781a8ccb72579d67871195313

Tx prefix hash: 717398c48846d8fc8aa12a80131d5f235a3a9569701215623a2f3e5eeeda8d74
Tx public key: 0c8fe276569a42b215234ca8273eef8517b81761d5858fe1d0d5956c11c33141
Timestamp: 1755030546 Timestamp [UCT]: 2025-08-12 20:29:06 Age [y:d:h:m:s]: 00:105:18:42:57
Block: 1345667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74949 RingCT/type: yes/0
Extra: 010c8fe276569a42b215234ca8273eef8517b81761d5858fe1d0d5956c11c33141021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4812f52893d09c87ea9a6b8d3f9db6c4acf7af707f3c53052dc8c17c67fee69f 0.600000000000 1833562 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": 1345677, "vin": [ { "gen": { "height": 1345667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4812f52893d09c87ea9a6b8d3f9db6c4acf7af707f3c53052dc8c17c67fee69f" } } ], "extra": [ 1, 12, 143, 226, 118, 86, 154, 66, 178, 21, 35, 76, 168, 39, 62, 239, 133, 23, 184, 23, 97, 213, 133, 143, 225, 208, 213, 149, 108, 17, 195, 49, 65, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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