Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c78d15aad60f73974d15c76de035b5ff82a90164754e9995505233a57f67ef41

Tx prefix hash: 7db16e73bfff39abc61f3fa3c5fadc5e92b2f92dc40df798bbdaa05a87a7d106
Tx public key: a6ead33d04aedd8c97cb1e422f202d00d37cff1d2f465c70c399fcf09eaafb2d
Timestamp: 1710073833 Timestamp [UCT]: 2024-03-10 12:30:33 Age [y:d:h:m:s]: 01:100:11:15:16
Block: 975267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332708 RingCT/type: yes/0
Extra: 01a6ead33d04aedd8c97cb1e422f202d00d37cff1d2f465c70c399fcf09eaafb2d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3009546f7c09d88772842ae2823f616dd77c39e815c4b8d34f142222ca10d322 0.600000000000 1435238 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": 975277, "vin": [ { "gen": { "height": 975267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3009546f7c09d88772842ae2823f616dd77c39e815c4b8d34f142222ca10d322" } } ], "extra": [ 1, 166, 234, 211, 61, 4, 174, 221, 140, 151, 203, 30, 66, 47, 32, 45, 0, 211, 124, 255, 29, 47, 70, 92, 112, 195, 153, 252, 240, 158, 170, 251, 45, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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