Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ffa3bf32a721cfae0281b720aaf72c51cc4be9d61d13290be0b4bb5f924d4a

Tx prefix hash: b79570a15a5343542fbdc98445a02cf844eea1502af79da384507114752a14a7
Tx public key: 5589f5ea16cfb9aca4a6d611b1a025dc23c27f8aadd5bdd4ea5e710bd94bf181
Timestamp: 1725756661 Timestamp [UCT]: 2024-09-08 00:51:01 Age [y:d:h:m:s]: 00:228:11:19:57
Block: 1105281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163144 RingCT/type: yes/0
Extra: 015589f5ea16cfb9aca4a6d611b1a025dc23c27f8aadd5bdd4ea5e710bd94bf181021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e7051ce16592139764e3a0323b15b6e1693a4f5e5bc1bdff1553872371d78b9 0.600000000000 1582622 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": 1105291, "vin": [ { "gen": { "height": 1105281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e7051ce16592139764e3a0323b15b6e1693a4f5e5bc1bdff1553872371d78b9" } } ], "extra": [ 1, 85, 137, 245, 234, 22, 207, 185, 172, 164, 166, 214, 17, 177, 160, 37, 220, 35, 194, 127, 138, 173, 213, 189, 212, 234, 94, 113, 11, 217, 75, 241, 129, 2, 17, 0, 0, 0, 4, 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