Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a0674c624f8784dc323d87ca9b339a79f5baa473d000839e274634c2fbe4640

Tx prefix hash: 5e44630619f5b3f21a059fbedb0dad42bcf448340f0744ce5cce2b5619da4f68
Tx public key: dd314a61c8a8a2aa6a91329c541c5466a9b6b890a79146c0316cdbcfef2edc4d
Timestamp: 1738307233 Timestamp [UCT]: 2025-01-31 07:07:13 Age [y:d:h:m:s]: 00:040:18:28:34
Block: 1208910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29164 RingCT/type: yes/0
Extra: 01dd314a61c8a8a2aa6a91329c541c5466a9b6b890a79146c0316cdbcfef2edc4d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1fe962bc89bc684a5a0a712a10284c8c3752d5b058b30c20958d0397f15e451 0.600000000000 1695647 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": 1208920, "vin": [ { "gen": { "height": 1208910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1fe962bc89bc684a5a0a712a10284c8c3752d5b058b30c20958d0397f15e451" } } ], "extra": [ 1, 221, 49, 74, 97, 200, 168, 162, 170, 106, 145, 50, 156, 84, 28, 84, 102, 169, 182, 184, 144, 167, 145, 70, 192, 49, 108, 219, 207, 239, 46, 220, 77, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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