Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76c8b4a5df59204df8374543266a3ee44b1593e99fdbc874ace4dc7e3e6dca2f

Tx prefix hash: b5f31292492c34cfb22936465dbd7a9bbb8f9617c7c5e84ee579abc35d20d282
Tx public key: 66dc66f2e2c87c7e25e799cb3f860851a9671428e0dec4812551464e6fab2023
Timestamp: 1745877856 Timestamp [UCT]: 2025-04-28 22:04:16 Age [y:d:h:m:s]: 00:242:22:30:45
Block: 1271583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171391 RingCT/type: yes/0
Extra: 0166dc66f2e2c87c7e25e799cb3f860851a9671428e0dec4812551464e6fab20230211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d88893ec258c45b92078a3f56e3e84db994094ee715d0ebc976591535121ab9 0.600000000000 1758848 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": 1271593, "vin": [ { "gen": { "height": 1271583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d88893ec258c45b92078a3f56e3e84db994094ee715d0ebc976591535121ab9" } } ], "extra": [ 1, 102, 220, 102, 242, 226, 200, 124, 126, 37, 231, 153, 203, 63, 134, 8, 81, 169, 103, 20, 40, 224, 222, 196, 129, 37, 81, 70, 78, 111, 171, 32, 35, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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