Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc074391609cbfec31b962ea3c093b11e5c475dadc4877bdb559a0a9a62b0756

Tx prefix hash: babe50bc25fef31cf255647ef004f32dfa4632525e65e8224192cad6371d6c7a
Tx public key: a3ae541d4e9dc9ce4521d0464e81e144d05739d7079a7ab052ca45a678f500eb
Timestamp: 1730057099 Timestamp [UCT]: 2024-10-27 19:24:59 Age [y:d:h:m:s]: 00:148:01:07:33
Block: 1140893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105597 RingCT/type: yes/0
Extra: 01a3ae541d4e9dc9ce4521d0464e81e144d05739d7079a7ab052ca45a678f500eb021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af9a66c447e634d4006a8cb7b0330c5eb01521e1ea7b5981d8fd86747d61e7f5 0.600000000000 1624696 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": 1140903, "vin": [ { "gen": { "height": 1140893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af9a66c447e634d4006a8cb7b0330c5eb01521e1ea7b5981d8fd86747d61e7f5" } } ], "extra": [ 1, 163, 174, 84, 29, 78, 157, 201, 206, 69, 33, 208, 70, 78, 129, 225, 68, 208, 87, 57, 215, 7, 154, 122, 176, 82, 202, 69, 166, 120, 245, 0, 235, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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