Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c9cdc9d1c6e105b8ac70bea2a164ad6d1746867a594ec529b31715fc8cd3210

Tx prefix hash: bb844ef87fb28527f53c551d8d0cec4ead38b04bfae2eeca9e7350eb32c907a9
Tx public key: f5e268e72bcd4aa47009ae23a42e2232275a2562a40caf4275e504e20363d493
Timestamp: 1710890060 Timestamp [UCT]: 2024-03-19 23:14:20 Age [y:d:h:m:s]: 01:231:02:36:33
Block: 982047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423834 RingCT/type: yes/0
Extra: 01f5e268e72bcd4aa47009ae23a42e2232275a2562a40caf4275e504e20363d49302110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 975728ee3a70bf70fc675bf6f779e955ff1f9527d47e973fc1996f9413ae5efe 0.600000000000 1442150 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": 982057, "vin": [ { "gen": { "height": 982047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "975728ee3a70bf70fc675bf6f779e955ff1f9527d47e973fc1996f9413ae5efe" } } ], "extra": [ 1, 245, 226, 104, 231, 43, 205, 74, 164, 112, 9, 174, 35, 164, 46, 34, 50, 39, 90, 37, 98, 164, 12, 175, 66, 117, 229, 4, 226, 3, 99, 212, 147, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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