Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c67990bf9315b33cd7e414cdd8818e91e4a46d78b08908363bb57156364155

Tx prefix hash: dfc6e93a93001e7a5739030e6e437829dfe148de490149761e2c34a61aeaf0e6
Tx public key: 1e351b6716d777952d93185c68a525d14b4b83d88128d2591c4610a5f3da6669
Timestamp: 1736844815 Timestamp [UCT]: 2025-01-14 08:53:35 Age [y:d:h:m:s]: 00:155:12:36:49
Block: 1197062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110849 RingCT/type: yes/0
Extra: 011e351b6716d777952d93185c68a525d14b4b83d88128d2591c4610a5f3da66690211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a5b500630f331503223a0c2b77c8bbbfd92910dc9a3dc2cd489f1b7a62af2f4 0.600000000000 1683667 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": 1197072, "vin": [ { "gen": { "height": 1197062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a5b500630f331503223a0c2b77c8bbbfd92910dc9a3dc2cd489f1b7a62af2f4" } } ], "extra": [ 1, 30, 53, 27, 103, 22, 215, 119, 149, 45, 147, 24, 92, 104, 165, 37, 209, 75, 75, 131, 216, 129, 40, 210, 89, 28, 70, 16, 165, 243, 218, 102, 105, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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