Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f3e833fb79fb8bb2381d7b75278130e75ae5b158f961d88453eb693847fd67d

Tx prefix hash: 39279ae0a66f71df0db7115c61de332b1a6314583064f9670f0878e4361066c9
Tx public key: bdf768a7e525ba1e696567728841a6ae65fdffebf81e59b6fcb76cab8a705e2f
Timestamp: 1731150654 Timestamp [UCT]: 2024-11-09 11:10:54 Age [y:d:h:m:s]: 00:128:01:21:48
Block: 1149915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91355 RingCT/type: yes/0
Extra: 01bdf768a7e525ba1e696567728841a6ae65fdffebf81e59b6fcb76cab8a705e2f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 590ef8c80f04c65127e6992e57e8cae62c7dc4e2344813348d8ec46ff68c8bd9 0.600000000000 1635092 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": 1149925, "vin": [ { "gen": { "height": 1149915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "590ef8c80f04c65127e6992e57e8cae62c7dc4e2344813348d8ec46ff68c8bd9" } } ], "extra": [ 1, 189, 247, 104, 167, 229, 37, 186, 30, 105, 101, 103, 114, 136, 65, 166, 174, 101, 253, 255, 235, 248, 30, 89, 182, 252, 183, 108, 171, 138, 112, 94, 47, 2, 17, 0, 0, 0, 1, 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