Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd4e42b71178b2dab6f6ca34d850b1f6d47900c74d5aa1031f8e947fa153fa56

Tx prefix hash: ace69f9c66667efdd63732b17dedf446dbe4c803371f26bfd36feb72de01eea3
Tx public key: cba790a7a224e4037356c5e44ab509a9da542161d1d30c62c9a8353d90b215b9
Timestamp: 1695961859 Timestamp [UCT]: 2023-09-29 04:30:59 Age [y:d:h:m:s]: 01:181:19:25:13
Block: 858476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390980 RingCT/type: yes/0
Extra: 01cba790a7a224e4037356c5e44ab509a9da542161d1d30c62c9a8353d90b215b9021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.878036734000 dcy

stealth address amount amount idx
00: fb9560b80dce54be3168a9ee2d02353e859b6096103a290f563eff7d9512c0da 0.878036734000 1312652 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": 858486, "vin": [ { "gen": { "height": 858476 } } ], "vout": [ { "amount": 878036734, "target": { "key": "fb9560b80dce54be3168a9ee2d02353e859b6096103a290f563eff7d9512c0da" } } ], "extra": [ 1, 203, 167, 144, 167, 162, 36, 228, 3, 115, 86, 197, 228, 74, 181, 9, 169, 218, 84, 33, 97, 209, 211, 12, 98, 201, 168, 53, 61, 144, 178, 21, 185, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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