Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ce46d1430839f02e3b18c0cf614650c4badf2fee53f0a76c799dad38a8d8596

Tx prefix hash: b8a8fafab455cc08399adfa3a392aa392c450c384fdcd345b318e0b113b1c04c
Tx public key: 34782e032d2ffccda4452da2e6d25d8f4274616424c7d6668be6efbfbfd2cd70
Timestamp: 1718471871 Timestamp [UCT]: 2024-06-15 17:17:51 Age [y:d:h:m:s]: 00:278:04:45:15
Block: 1044901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198797 RingCT/type: yes/0
Extra: 0134782e032d2ffccda4452da2e6d25d8f4274616424c7d6668be6efbfbfd2cd7002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d20f52529da5673332af5b2fd1d2973de273955b0adf1ab7fff24f24247dcb1 0.600000000000 1514334 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": 1044911, "vin": [ { "gen": { "height": 1044901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d20f52529da5673332af5b2fd1d2973de273955b0adf1ab7fff24f24247dcb1" } } ], "extra": [ 1, 52, 120, 46, 3, 45, 47, 252, 205, 164, 69, 45, 162, 230, 210, 93, 143, 66, 116, 97, 100, 36, 199, 214, 102, 139, 230, 239, 191, 191, 210, 205, 112, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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