Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 558501f2c7e015bce9264174f651218f31078de1c59837db16f5665e2cb1d2f4

Tx prefix hash: 9d64f086d14d9cfc9d5b27e49dff09164bc98b03753ff2c3db4e7173de434998
Tx public key: d75e6215795d8b8661a8686ea7a1a71444236c97ce1f1a54887170300c259f3b
Timestamp: 1724078099 Timestamp [UCT]: 2024-08-19 14:34:59 Age [y:d:h:m:s]: 00:233:21:57:33
Block: 1091370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167050 RingCT/type: yes/0
Extra: 01d75e6215795d8b8661a8686ea7a1a71444236c97ce1f1a54887170300c259f3b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4b31fd2dd985bb5394ab712bc38f47ad0b2969c258d786d37da98415b52521 0.600000000000 1566001 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": 1091380, "vin": [ { "gen": { "height": 1091370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4b31fd2dd985bb5394ab712bc38f47ad0b2969c258d786d37da98415b52521" } } ], "extra": [ 1, 215, 94, 98, 21, 121, 93, 139, 134, 97, 168, 104, 110, 167, 161, 167, 20, 68, 35, 108, 151, 206, 31, 26, 84, 136, 113, 112, 48, 12, 37, 159, 59, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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