Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8aeaa9d1a641a1523db5c4e4ce453107a72e29132ab8ed0275c32c21edc4c09

Tx prefix hash: 28edb941790993cd9c5cac940c46d93183a02b0660ab5b7c44ee7ca69a0ca115
Tx public key: 3ab00372a0ba0485e069fda91d3704726f40eb9113ad228fce8c8daf241ab8ff
Timestamp: 1700813464 Timestamp [UCT]: 2023-11-24 08:11:04 Age [y:d:h:m:s]: 01:001:18:25:09
Block: 898488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262618 RingCT/type: yes/0
Extra: 013ab00372a0ba0485e069fda91d3704726f40eb9113ad228fce8c8daf241ab8ff0211000000024b8f5122000000000000000000

1 output(s) for total of 0.647047646000 dcy

stealth address amount amount idx
00: b621f4805bc4a3076d41b6c97cffddca55565ea59e96e713e5fb125cac79b30a 0.647047646000 1354909 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": 898498, "vin": [ { "gen": { "height": 898488 } } ], "vout": [ { "amount": 647047646, "target": { "key": "b621f4805bc4a3076d41b6c97cffddca55565ea59e96e713e5fb125cac79b30a" } } ], "extra": [ 1, 58, 176, 3, 114, 160, 186, 4, 133, 224, 105, 253, 169, 29, 55, 4, 114, 111, 64, 235, 145, 19, 173, 34, 143, 206, 140, 141, 175, 36, 26, 184, 255, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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