Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b10174aaa6dc07ba6721a76b7263e5a19863abfbfbc83a0a22bfee0c0f460036

Tx prefix hash: 851c4fef2f0b0bc9cf77cce095ef96f3e96a79c3aa59a0c184954e393db2d2d3
Tx public key: d698e1f6cfc8b201438a963d8d0ff125dcf2a9cef708695aee6c50e59ddc2a7d
Timestamp: 1696762091 Timestamp [UCT]: 2023-10-08 10:48:11 Age [y:d:h:m:s]: 02:031:09:30:44
Block: 865113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542052 RingCT/type: yes/0
Extra: 01d698e1f6cfc8b201438a963d8d0ff125dcf2a9cef708695aee6c50e59ddc2a7d021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.834682946000 dcy

stealth address amount amount idx
00: 1c78b250d2d3b140620742a127ddf7b91fa72a634863512b275229d476a0839c 0.834682946000 1319639 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": 865123, "vin": [ { "gen": { "height": 865113 } } ], "vout": [ { "amount": 834682946, "target": { "key": "1c78b250d2d3b140620742a127ddf7b91fa72a634863512b275229d476a0839c" } } ], "extra": [ 1, 214, 152, 225, 246, 207, 200, 178, 1, 67, 138, 150, 61, 141, 15, 241, 37, 220, 242, 169, 206, 247, 8, 105, 90, 238, 108, 80, 229, 157, 220, 42, 125, 2, 17, 0, 0, 0, 4, 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