Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f479fd0c74479136ab27f97d71046d864528ef49f5f65207367e92bcd99f5cbf

Tx prefix hash: 22485e9f12ba08cc422744fe251973494dc2edf5cfc0a203fbfada73b0ffc007
Tx public key: 78dfeb9f130710d73c746e30b43ca1e232c556da957edf3c7180e3a5a90e1dcc
Timestamp: 1720654975 Timestamp [UCT]: 2024-07-10 23:42:55 Age [y:d:h:m:s]: 00:279:06:44:39
Block: 1062991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199537 RingCT/type: yes/0
Extra: 0178dfeb9f130710d73c746e30b43ca1e232c556da957edf3c7180e3a5a90e1dcc021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5ae23029a9e873e24954a4fb983b665dcad8dbefc4ebdea6e97f65cc25c23c7 0.600000000000 1533502 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": 1063001, "vin": [ { "gen": { "height": 1062991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5ae23029a9e873e24954a4fb983b665dcad8dbefc4ebdea6e97f65cc25c23c7" } } ], "extra": [ 1, 120, 223, 235, 159, 19, 7, 16, 215, 60, 116, 110, 48, 180, 60, 161, 226, 50, 197, 86, 218, 149, 126, 223, 60, 113, 128, 227, 165, 169, 14, 29, 204, 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