Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 282d38bc832466df8457b2fe5dddb4b70bc871107f7c7aab307a575932bfc035

Tx prefix hash: ea987f79834c11218bb1f685695a2fb1c017c8270ef892662e6bc3abc6ed6b3e
Tx public key: 56f8a52470dd764edeb45c078929f8d582353fa702134c34c43961fea6fd43a9
Timestamp: 1693598310 Timestamp [UCT]: 2023-09-01 19:58:30 Age [y:d:h:m:s]: 01:176:06:34:14
Block: 838855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387064 RingCT/type: yes/0
Extra: 0156f8a52470dd764edeb45c078929f8d582353fa702134c34c43961fea6fd43a90211000000104b8f5122000000000000000000

1 output(s) for total of 1.019824011000 dcy

stealth address amount amount idx
00: b7f10eecdf6d9b797e8611a99f8cb8cdf69d25ee423380c3adf1b67c2cbf65ee 1.019824011000 1291645 of 0

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": 838865, "vin": [ { "gen": { "height": 838855 } } ], "vout": [ { "amount": 1019824011, "target": { "key": "b7f10eecdf6d9b797e8611a99f8cb8cdf69d25ee423380c3adf1b67c2cbf65ee" } } ], "extra": [ 1, 86, 248, 165, 36, 112, 221, 118, 78, 222, 180, 92, 7, 137, 41, 248, 213, 130, 53, 63, 167, 2, 19, 76, 52, 196, 57, 97, 254, 166, 253, 67, 169, 2, 17, 0, 0, 0, 16, 75, 143, 81, 34, 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