Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c356a13997a487f0f7507c7f57a67434bd9ff70fe341d6710ba26c4863319fe

Tx prefix hash: d27c083b412852e465509409bb605bae51ab2d0fcb93679412966eedd0fba178
Tx public key: 9674531c6954ea9a5f3b544261235df1e2c0f88771332ab6249932d8e851a9de
Timestamp: 1715638009 Timestamp [UCT]: 2024-05-13 22:06:49 Age [y:d:h:m:s]: 00:331:00:33:15
Block: 1021387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236614 RingCT/type: yes/0
Extra: 019674531c6954ea9a5f3b544261235df1e2c0f88771332ab6249932d8e851a9de0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ca2e3f9c867fe17bf7e7c9150d3298832f64f5d0f03cc1b0e3f490f805d3e18 0.600000000000 1485696 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": 1021397, "vin": [ { "gen": { "height": 1021387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ca2e3f9c867fe17bf7e7c9150d3298832f64f5d0f03cc1b0e3f490f805d3e18" } } ], "extra": [ 1, 150, 116, 83, 28, 105, 84, 234, 154, 95, 59, 84, 66, 97, 35, 93, 241, 226, 192, 248, 135, 113, 51, 42, 182, 36, 153, 50, 216, 232, 81, 169, 222, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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