Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967f603150e3f26e69ac088533938183fd7533ac964e367785785e0e1df8f9d3

Tx prefix hash: ee6a24b2a59db6646488afe28a6a5b3930a5dbb922c96dd90c6d9c10c313932f
Tx public key: 27e8af6e722769d64392a4d6a841fa7e02eef99b2641639f8d71fe718c47829f
Timestamp: 1683614142 Timestamp [UCT]: 2023-05-09 06:35:42 Age [y:d:h:m:s]: 01:336:21:07:12
Block: 756158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502000 RingCT/type: yes/0
Extra: 0127e8af6e722769d64392a4d6a841fa7e02eef99b2641639f8d71fe718c47829f021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.916614829000 dcy

stealth address amount amount idx
00: be096fe5235d39a1d345ff7f5a682f77dd597506807c85697cf12fc6692a715f 1.916614829000 1204509 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": 756168, "vin": [ { "gen": { "height": 756158 } } ], "vout": [ { "amount": 1916614829, "target": { "key": "be096fe5235d39a1d345ff7f5a682f77dd597506807c85697cf12fc6692a715f" } } ], "extra": [ 1, 39, 232, 175, 110, 114, 39, 105, 214, 67, 146, 164, 214, 168, 65, 250, 126, 2, 238, 249, 155, 38, 65, 99, 159, 141, 113, 254, 113, 140, 71, 130, 159, 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